-
Notifications
You must be signed in to change notification settings - Fork 47
fix: Deprecate cargo_bin (runtime version) #248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Pull Request Test Coverage Report for Build 18889989393Details
💛 - Coveralls |
| /// [`Command`]: std::process::Command | ||
| #[deprecated( | ||
| since = "2.1.0", | ||
| note = "incompatible with a custom cargo build-dir, see instead `cargo::cargo_bin!`" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am confused by this deprecation notice. Does "custom cargo build-dir" mean custom target directory, e.g., as one would specify with CARGO_TARGET_DIR?
The incompatibility is not related to changing the build directory within the target directory (e.g., target/debug/build), correct?
If it is neither of these, could you please point me to a reference?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rust 1.91 split a build-dir out of target-dir with the default falling back to target-dir, for now though I hope to change that in the future.
See https://doc.rust-lang.org/cargo/reference/build-cache.html
fix: Deprecate cargo_bin (runtime version)
The problem with this is we can't compile doctests using
cargo_bin!. Unsure what the right answer is.